home *** CD-ROM | disk | FTP | other *** search
- Path: god.bel.alcatel.be!nlev00!barnhoorn
- From: barnhoorn@nlev00 ()
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Messages vs. Semaphores for external clocking
- Date: 4 Apr 1996 06:56:28 GMT
- Organization: Alcatel Bell
- Distribution: world
- Message-ID: <4jvrqs$hk0@btmpjg.god.bel.alcatel.be>
- References: <4ju349$r1e@sparky.navsea.navy.mil>
- Reply-To: barnhoorn@nlev00 ()
- NNTP-Posting-Host: 138.203.178.61
- X-Newsreader: mxrn 6.18-10
-
-
- In article <4ju349$r1e@sparky.navsea.navy.mil>, matuli_a@marlin.navsea.navy.mil (Alex Matulich 03T1 602-6691) writes:
- >I am wondering what is the most efficient way for one task to make data
- >available to another task. I can do this by passing messages, or by
- >setting up a semaphore to provide a common area of memory accessible by
- >both tasks.
- >
- [..description removed..]
-
- Use global data, which your subtask fills with the timer-values,
- and the parent process reads. Disable() and Enable() multitasking
- when performing such a critical action (reading or writing from the
- global data). No message port or semaphore needed.
-
- --
- ---------------------------------------------------------------------------
- Jaco Barnhoorn barnie@xs4all.nl
- Software Test Engineer barnhoorn%nlev00@btmv56.se.bel.alcatel.be
- Alcatel Telecom Systems
- Rijswijk, The Netherlands
- ---------------------------------------------------------------------------
-